Handheld device for on-site datacenter management

ABSTRACT

In various exemplary embodiments, a system and associated method to provide management of a plurality of electronic elements in a datacenter is disclosed. The system includes a datacenter management system coupled to a wireless network to receive information regarding a spatial location of a handheld device within the datacenter. The datacenter management system provides information to the handheld device related to each of the plurality of electronic elements. The datacenter management system includes a management processor to process information related to each of the plurality of electronic elements and a database to store information related to each of the plurality of electronic elements.

PRIORITY

This application is a continuation of and claims the benefit of priorityunder to U.S. patent application Ser. No. 12/755,289, filed on Apr. 6,2010, which is hereby incorporated by reference herein in its entirety.

TECHNICAL FIELD

The present application relates generally to the field of computertechnology and, in a specific exemplary embodiment, to a system andmethod of locating and maintaining elements in a datacenter.

BACKGROUND

In a variety of medium and large-scale environments where electronicequipment is used, numerous pieces of equipment such as servers,routers, switches, and other network equipment must be serviced,upgraded, installed, and maintained. For example, in a multi-sellerelectronic marketplace, one or more sellers can list their inventory andbuyers can purchase the inventory via a networked system, such as overthe Internet. The electronic marketplace example can include on-linestores including wholesalers or retailers. In other forms, theelectronic marketplace can include banks, world-wide distributedenterprise systems, or on-line auction-sites. In all cases, some degreeof equipment installation and maintenance must be implemented to ensurereliability of the electronic environment.

BRIEF DESCRIPTION OF DRAWINGS

Various ones of the appended drawings merely illustrate exemplaryembodiments of the present invention and cannot be considered aslimiting its scope.

FIG. 1 is a block diagram illustrating an exemplary embodiment of ahigh-level client-server-based network architecture diagram in whichvarious embodiments of inventive subject matter described herein may beutilized, the network architecture depicts a system used to processend-user queries;

FIG. 2 is a block diagram illustrating an exemplary embodiment of ahigh-level depiction of a device used for on-site datacenter management;

FIG. 3A is a block diagram illustrating an exemplary embodiment ofclient architecture employed by the device of FIG. 2;

FIG. 3B shows an exemplary embodiment of an electronic interface systemusable with the client architecture of FIG. 2;

FIG. 4 is an exemplary view of a mapping feature within a datacenter asillustrated on the device of FIG. 2;

FIG. 5A is an exemplary view of a three-dimensional row view within thedatacenter as illustrated on the device of FIG. 2;

FIG. 5B is an exemplary view of a rack view within the datacenter asillustrated on the device of FIG. 2;

FIG. 5C is an exemplary view of a cabling overlay view within thedatacenter as illustrated on the device of FIG. 2;

FIG. 6 is an exemplary embodiment of a high-level model depicting thedatacenter;

FIG. 7 is an exemplary embodiment illustrating a radio location systemwithin the datacenter; and

FIG. 8 is a simplified block diagram of a machine in an exemplary formof a computing system within which a set of instructions, for causingthe machine to perform any one or more of the methodologies discussedherein, may be executed.

DETAILED DESCRIPTION

The description that follows includes illustrative systems, methods,techniques, instruction sequences, and computing machine programproducts that embody at least portions of the inventive subject matter.In the following description, for purposes of explanation, numerousspecific details are set forth to provide an understanding of variousembodiments of the inventive subject matter. It will be evident,however, to those skilled in the art that embodiments of the inventivesubject matter may be practiced without these specific details. Further,well-known instruction instances, protocols, structures, circuits, andtechniques have not been shown in detail.

As used herein, the term “or” may be construed in either an inclusive oran exclusive sense. Similarly, the term “exemplary” is construed merelyto mean an example of something or an exemplar and not necessarily apreferred or ideal means of accomplishing a goal. Additionally, althoughvarious exemplary embodiments discussed below focus on an electronicdatacenter environment, the embodiments are given merely for clarity indisclosure. Thus, any type of electronic environment may employ variousembodiments of the handheld device and method for on-site datacentermanagement described herein. Thus, various types of electronicenvironment using the device or method are considered as being within ascope of one or more embodiments of the inventive subject matter.

In an exemplary embodiment, a system to provide management of aplurality of electronic elements in a datacenter is disclosed. Thesystem includes a datacenter management system, coupled to a wirelessnetwork that receives information regarding a spatial location of ahandheld device within the datacenter. The datacenter management systemprovides information to the handheld device related to each of theplurality of electronic elements. The datacenter management systemincludes a management processor to process information related to eachof the plurality of electronic elements and a database to storeinformation related to each of the plurality of electronic elements.

In an exemplary embodiment, a system to provide management of aplurality of electronic elements in a datacenter is disclosed. Thesystem includes a datacenter management means, coupled to a wirelessnetwork, for receiving information regarding a spatial location of ahandheld device within the datacenter. The datacenter management meansalso provides information to the handheld device related to each of theplurality of electronic elements. A processing means processesinformation related to each of the plurality of electronic elements anda storage means stores information related to each of the plurality ofelectronic elements.

In an exemplary embodiment, a method to provide management of aplurality of electronic elements in a datacenter is disclosed. Themethod includes receiving information regarding a spatial location of ahandheld device within the datacenter, retrieving information related toeach the plurality of electronic elements based on the spatial locationof the handheld device within the datacenter, and processing andtransmitting the information related to each of the plurality ofelectronic elements to the handheld device.

In another exemplary embodiment, a machine-readable storage mediumincluding a plurality of instructions that, when executed by one or moreprocessors, causes at least one of the one or more processors to performa method to provide management of a plurality of electronic elements ina datacenter is disclosed. The method includes receiving informationregarding a spatial location of a handheld device within the datacenter,retrieving information related to each of the plurality of electronicelements based on the spatial location of the handheld device within thedatacenter, and processing and transmitting the information related toeach of the plurality of electronic elements to the handheld device.Each of these exemplary embodiments, and others, is discussed in detail,below.

Overview

Management of datacenters generally requires site services employees toperform manual tasks within the datacenters. When the datacenter islarge, the tasks are more challenging and can be performed faster withthe support of a handheld device, such as a smart phone (e.g., aBlackberry® or iPhone®), personal data assistant, or other devicecapable of connecting wirelessly to other devices and providing agraphical or textual display to a user of the device (e.g., an employeewithin the datacenter). Tasks performed manually within a datacenter arebecoming more complex with an increase in scale and virtualization ofthe infrastructure. Some of the tasks may require precise identificationof infrastructure elements, as well as real time information about theelements. By using a handheld device connected to the managementsystems, and equipped with sensors such as a global positioning system(GPS), a magnetometer, an inclination sensor, or other instrumentationknown independently in the art, various embodiments of the inventivesubject matter described herein provide assistance to the employeesperforming the management tasks.

The handheld device assists the employee with finding a location ofvarious electronic and other assets, assessing the status of the assets,or providing guidance based on, for example, just-in-time informationfor the placement, replacement, maintenance, or retirement of one ormore of the assets.

The handheld device may use sensors to assists with tasks such as assetidentification, positioning, and relocation or maintenance within thedatacenter. Information can be downloaded to the device for identifyingthe asset within a row or a rack within the datacenter. As noted above,the handheld device may use wireless connectivity to retrieve datacentermaps, row and rack inventories, status of assets, or guidance withregard to particular tasks to be performed.

An Exemplary Datacenter Environment

With reference to FIG. 1, a high-level network diagram of an exemplaryembodiment of a system 100 with a client-server architecture includes afirst client machine 101, a second client machine 107, a third clientmachine 111, a network 117 (e.g., the Internet), and an informationstorage and retrieval platform 120. In this embodiment, the informationstorage and retrieval platform 120 constitutes a commerce platform orcommerce server and provides server-side functionality, via the network117, to the first 101, second 107, and third 111 client machines. Aprogrammatic client 103 in the form of authoring modules 105 executes onthe first client machine 101. A first web client 109 (e.g., a browser,such as the Internet Explorer browser developed by Microsoft Corporationof Redmond, Wash.) executes on the second client machine 107. A secondweb client 113 executes on the third client machine 111. Additionally,the first client machine 101 is coupled to one or more databases 115.

Turning to the information storage and retrieval platform 120, anapplication program interface (API) server 121 and a web server 123 arecoupled to, and provide programmatic and web interfaces respectively to,one or more application servers 125. The application servers 125 hostone or more modules 127 (e.g., modules, applications, engines, etc.).The application servers 125 are, in turn, coupled to one or moredatabase servers 129 facilitating access to one or more informationstorage databases 131. The one or more modules 127 provide a number ofinformation storage and retrieval functions and services to usersaccessing the information storage and retrieval platform 120. The one ormore modules 127 are discussed in more detail, below.

While the exemplary system 100 of FIG. 1 employs a client-serverarchitecture, a skilled artisan will recognize that the presentdisclosure is not limited to such an architecture. The exemplary system100 could equally well find application in, for example, a distributed,or peer-to-peer, architecture system. The one or more modules 127 andthe authoring modules 105 may also be implemented as standalone softwareprograms, which do not necessarily have networking capabilities.

The first 109 and second 113 web clients access the one or more modules127 via the web interface supported by the web server 123. Similarly,the programmatic client 103 accesses the various services and functionsprovided by the one or more modules 127 via the programmatic interfaceprovided by the API server 121. The programmatic client 103 is, forexample, a seller application (e.g., the “Turbo Lister 2” applicationdeveloped by eBay Inc., of San Jose, Calif.) enabling sellers to authorand manage data items or listings on the information storage andretrieval platform 120 in an off-line manner. Further, batch-modecommunications can be performed between the programmatic client 103 andthe information storage and retrieval platform 120. In addition, theprogrammatic client 103 can include, as previously indicated, theauthoring modules 105 used to author, generate, analyze, and publishdomain rules and aspect rules. The domain and aspect rules are used inthe information storage and retrieval platform 120 to structure the dataitems and transform queries. Such domain and aspect rules are knownindependently in the art.

Referring now to FIG. 2, a block diagram illustrates a high-leveldepiction of a datacenter 200 utilizing on-site datacenter management.The datacenter 200 is shown to include a handheld device 201 to receivepertinent information (described in detail, below) about the datacenter200 through a datacenter management system 205 coupled to a wirelessnetwork 203. The datacenter 200 may be located, at least partially,within one or more physical facilities. The datacenter 200 can include,for example, a traditional computing facility or an internal or externalcloud computing facility. The datacenter management system 205 includesa management processor 209 on which various hardware and softwarecomponents, discussed herein, may be located. The management processor209 may include, for example, one or more processors and a database (notshown explicitly). The database includes information related to aspatial location (e.g., datacenter, row, rack, chassis, etc.) of anumber of electronic components, assets, or elements. Additionally, thedatabase can include information related to electrical specifications,cabling, maintenance dates, updates, software and firmware versionnumbers, and so on for each of the racks or electronic elements withinthe datacenter. In an exemplary embodiment, the database may be locatedremotely from the management processor 209 or as a stand-alone unit. Anoptional radio location system 207, operating within the datacenter 200if present, is shown to include several antennas 211A . . . 211N coupledto a positioning computer 213.

System Description

The handheld device 201 may include a cellular communications radio(e.g., global system for mobile communications (GSM)) capable of datatransmission (e.g., using general packet radio service (GPRS)) connectedto the Internet through a cellular phone provider network (not shown).The handheld device 201 may also include a global position system (GPS).These characteristics are discussed in more detail, below. The handhelddevice 201 may have other means of data transmission including WIFIusing, for example, a wireless networking standard such as IEEE802.11-2007 (e.g., 802.11b, 802.11g, or 802.11n). The handheld device201 includes multiple internal sensors (not shown but found commonly inmany contemporary communications devices such as smart phones). Themultiple internal sensors may be based on, for example, accelerometersand can detect positional information including inclination,orientation, and position. In a specific exemplary embodiment, thehandheld device 201 is a smart phone.

To facilitate some of the data acquisition tasks described herein, thehandheld device 201 may also include a camera and optional readers toread optical (e.g., bar codes) and non-optical (e.g., radio-frequencyidentification (RFID) tags) identification labels. A client softwareapplication running in the handheld device 201, described below,provides a user with functionalities to perform various installation andmaintenance tasks of the datacenter management system 205. The clientsoftware application interacts with hardware of the handheld device 201,as well as with a management application residing on, for example, themanagement processor 209. The handheld device 201 thus interacts withthe management processor 209 through the wireless network 203.

In a situation where a physical facility makes a GPS portion of thehandheld device 201 unusable (e.g., due to blocked signals), theoptional radio location system 207 operates through the several antennas211A . . . 211N in the datacenter 200 to provide indoor positioning tothe handheld device 201. The several antennas 211A . . . 211N listen toradio transmissions of the handheld device 201 and, based on a relativereceiving time of the transmissions as processed and determined by thepositioning computer 213, determine a spatial position of the handhelddevice 201. The spatial position is sent back to the handheld device 201through the wireless network 203 to provide for more precisepositioning.

The handheld device 201 is assigned to an employee performing taskswithin the datacenter 200. The datacenter management system 205 providesa back end for the client software application running within thehandheld device 201. The management processor 209 provides support forthe spatial location of the handheld device 201 with regard tomanagement of infrastructure components within the datacenter 200. Themanagement processor 209 also provides inventory, topology, and statusfor all components within the datacenter 200 and guides a site servicesemployee carrying the handheld device 201 in the tasks to be performed.More detail on each of the components is provided below.

Handheld Device

In addition to functions described above, the handheld device 201provides radio communication with a cellular network to support voiceand data transmissions. Specific communications characteristics of thehandheld device 201 are not relevant as long as the performance (e.g.,availability, bandwidth, and latency) is sufficient for a givenapplication. For example, at a minimum, one application requirescommunications to function in an environment with a potentially highlevel of radio interference. In various exemplary embodiments, thehandheld device 201 operates on a wireless network radio to communicateelectronically, including data connectivity, with the wireless network203 within the datacenter 200. The data connectivity is used to accessvarious applications running on the management processor 209. Dataconnectivity can be accomplished through, for example, the wirelessnetwork 203, or, alternatively or in conjunction with, the Internet byusing a data portion of the cellular network (not shown).

With reference now to FIG. 3A, the handheld device 201 is shown toinclude a datacenter management client-software engine 301, a handheldsoftware development kit (SDK) interface 303, and a handheld devicehardware component 305. The handheld device hardware component 305 isshown to include a GPS component 313, a digital camera 315, a dataconnection component 317, and one or more position sensors 319.

The handheld device 201 also includes a display screen (not shown) todisplay graphics (such as photographs, maps, and wiring schematics).Thus, a resolution of the display screen should be sufficient torepresent the datacenter infrastructure without requiring an unnecessarypan out. The display screen may also be touch sensitive and may supportgestures like flipping pages, scrolling up or down, zooming in or out,or clicking or double clicking In certain embodiments, the displayscreen is able to support millions of colors to assist in properinterpretations of photographs and schematics.

The datacenter management client-software engine 301 is shown to includea gestures component 307, a mapping component 309, and an identificationcomponent 311. More details on the datacenter management client-softwareengine 301 are provided, below.

The handheld SDK interface 303 allows the datacenter managementclient-software engine 301 to interface with the handheld devicehardware component 305 of the handheld device 201. The handheld SDKinterface 303 is discussed in detail, below.

The one or more position sensors 319 provide a position in space of thehandheld device 201 to the management processor 209 (see FIG. 2). Theone or more position sensors 319 can either be located within or merelysupported by the handheld device 201. The one or more position sensors319 measure inclination of the handheld device 201, dynamically, todetect movements like the handheld device 201 pointing up or down, orsweeping from up to down (and vice versa). The one or more positionsensors 319 may also provide a magnetometer to measure the handhelddevice 201 pointing direction with regard to magnetic north,dynamically, to detect movements like pointing left or right, orsweeping from left to right (and vice versa). The handheld device 201may either provide or support additional sensors, or input ports to readidentification tags like RFID, iButton, and so on. These sensors may beindirectly connected to the handheld device 201 through a radio networklike Bluetooth. The handheld device 201 exposes these sensors, or thecollected identifiers, to the client software.

The digital camera 315 included in the handheld device hardwarecomponent 305 has a resolution sufficient to capture either linear ortwo-dimensional (2-D) bar code identification from a component withinthe datacenter 200. The handheld device 201 can present photographs tothe client software in real time or through a generation of picturefiles.

With reference again to the datacenter management client-software engine301, client software running on the handheld device 201 includes avariety of use cases. In one exemplary embodiment, the client softwareprovides a capability to the handheld device 201 to support various onesof the use cases listed, below.

In one use case, the client software provides for management of the taskqueue. In this case, users of the handheld device 201 (e.g., siteservice employees) log in and view one or more list of tasks assigned toeach of the users individually or assigned jointly to their group. Theusers can view a context required to perform the tasks and to manage thetask life cycle (e.g., acknowledge, update, close). The paradigm forthis view is similar to an email inbox.

In another use case, users receive notifications similar to instantmessages (IMs) or short messages (e.g., tweets) regarding alerts,broadcasts, or other messages. The notifications may be used for eitherurgent or non-urgent requests.

In another use case, users receive tasks related to racking and wiringof components. For example, when servers or racks are received on thedock, they need to be installed and wired according to very specificpolicies and procedures. Thus, a location of the rack, the ports, andpower connectors to be used will be calculated in real time based on thepolicies and procedures using a datacenter model and inventory storedon, for example, the management processor 209 (see FIG. 2.). The usersare provided with a datacenter map, rack map, and an overlay definingwhere and how the equipment should be installed to be compliant with thepre-defined procedures. Using the handheld device 201, the users nolonger need to “scan” the equipment to record the asset tags since allupdates are provided to the datacenter management system 205 (see FIG.2) in real-time or near real-time.

In another use case, if a datacenter infrastructure component needs tobe returned for repair, or retired from production, the site serviceemployees need to locate the equipment accurately in order to remove theproper component from production. The client software provides a map ofthe datacenter, and the rack, with an overlay identifying the particularcomponent to remove. In the execution of this use case, the user scansthe equipment to record the asset tags.

In another use case, site services employees may need to locate a pieceof equipment in order to perform maintenance, repair, or diagnosis. Theclient software provides a mechanism to locate the equipment andvalidate the current wiring and connectivity, based on a diagramcalculated from the datacenter model hosted on the datacenter managementsystem 205.

In another use case, an audit of a specific configuration within thedatacenter 200 (see FIG. 2) utilizes the handheld device 201 to performthe audit and discover components efficiently. In the execution of thisuse case, the user scans the equipment to record one or more associatedasset tags. The client software, in addition to existing business logic(e.g., asset management software) interacts with one or more devices ofthe handheld device hardware component 305 through the handheld SDKinterface 303.

With continuing reference to the datacenter management client-softwareengine 301, various aspects of the inventive subject matter within theclient software of the handheld device 201 are provided by threeadditional subsystems including the gestures component 307, the mappingcomponent 309, and the identification component 311. Each of the variousengines and components described may be hardware, software, or firmwarecomponents or a combination thereof

As discussed briefly above, a gestures component 307 ensures readyaccess to various components of the handheld device 201 by, for example,merely tapping or swiping a finger over the display screen. As a result,the gestures component 307 enhances efficiency of the user by improvingaccess to various items appearing on the display screen such as multiplepages of schematics and wiring diagrams.

The mapping component 309 provides the user with a map to an accuratelocation of the user within the datacenter 200 using, for example, thetriangulation features of the optional radio location system 207 (seeFIG. 2) or the GPS component 313. The map is displayed on the displayscreen of the handheld device 201. The mapping component 309 in thehandheld device 201 can be used for at least two purposes. First, alocation of components in the datacenter 200 and the items to beserviced or the location where new items need to be added may beidentified on a map representing the datacenter floor, rooms, row,racks, or other elements. The locational capabilities of the handhelddevice 201 are described in more detail, below. Secondly, a location ofthe user with regard to the datacenter 200 may be identified on the map.This capability is used to display or focus the display screen on anarea within the datacenter 200 in which the user is located. This can bea building, a floor, a room, a row, or a rack located in proximity tothe user. In cases where the handheld device 201 is providing theposition of the user, the client software uses the handheld SDKinterface 303 to retrieve the user position and display an appropriatemap. The maps themselves can be served on demand by, for example, thedatacenter management system 205. Depending on a zoom level of thedisplayed map, the maps may represent a datacenter, a room within thedatacenter, a rack row within the room, or a particular rack.

Also discussed above, the identification component 311 can couple thehandheld device 201 to, for example, optical or non-optical sensorswithin or supported by the handheld device 201. The handheld device 201can be used to scan components for either component identification orverification.

With reference now to FIG. 3B, a detailed exemplary embodiment 350 ofthe handheld SDK interface 303 of FIG. 3B is shown to include a handhelddevice code section 355, a common procedures section 353, and severalapplication program interface (API) driver sections 351. The handhelddevice code section 355 includes any software components, algorithms,etc., necessary to work with the handheld device 201. Thus, details ofthe handheld device code section 355 will vary from one handheld devicemanufacturer (e.g., a smart phone manufacturer) to another. However,details for interfacing any handheld device with software in general,and the several API driver sections 351 in particular, is knownindependently by one skilled in the art. Further, the handheld devicecode section 355 may be considered an open solution and is thus directlyopen to extension by the handheld device manufacturer.

Additionally, the common procedures section 353 provides an interfacefrom each of the several API driver sections 351. The common proceduressection 353 may be considered as a sub-component of the SDK interface300. SDK sub-components are known independently in the art and allow aprogrammer to create applications for enhancing operation of othersoftware or devices. Here, an operation of each API driver in theseveral API driver sections 351 is enhanced through the commonprocedures section 353 to operate with the handheld device 201. Detailsfor the common procedures section 353 vary depending upon detailsrequired by a handheld device manufacturer and a particular APIinterfacing with the handheld device 201. However, the skills requiredto write code within the common procedures section 353 are knownindependently in the art.

Referring now to FIG. 4, a display screen illustrates an exemplarymapping feature 400 on the handheld device 201 having a two-dimensionaldatacenter map 401 (e.g., a floor plan) showing a number of racklocations (e.g., Rack 1 to Rack 8) along with a relative location 403 ofa user of the handheld device 201 within the datacenter. In addition tothe number of rack locations, the two-dimensional datacenter map 401also shows the layout of the floor with various rows between the racklocations. The user can zoom in and zoom out using, for example,gestures supported by the handheld device 201.

With reference to FIG. 5A, when the user viewing a map at a row level,the exemplary display screen may change from the two-dimensionaldatacenter map 401 to a three-dimensional row-view display 500 of racksand rows. In a specific exemplary embodiment, the three-dimensionalrow-view display 500 is shown to include a first rack 501, a second rack503, a user 505, and a rack unit location 507. In this exemplaryembodiment, instead of or in addition to relying on the GPS to provide alocation, the magnetometer sensor (not shown explicitly) can be used topan left and right. The inclination sensor can also be used to “look” upor down within the datacenter.

Referring now to FIG. 5B, when the user 505 (FIG. 5A) approaches moreclosely to one or more of the objects present within the datacenter,such as the first rack 501 and pointing to a specific location on thefirst rack 501, the display may change to present an updated rack-view530. The updated rack-view 530 provides more details about the specificlocation within the first rack 501, such as the rack unit location 507to which the handheld device 201 is pointing or electricalspecifications and maintenance records for electrical elements orcomponents within the specific location within the first rack 501. Ifthe resolution of the positioning system is insufficient for thespecific location functionality to work properly, the user 505 may beable to default to an identification capability to scan a tag (not shownexplicitly) displayed on the pointed object, such as the rack unitlocation 507. The map will be updated to represent the identifiedobject. On top of the maps, overlays can be displayed based on aparticular configuration or level of zoom.

The types of features that can be displayed are use case dependent, butcan be, for example, rows or racks where new hardware needs to be added.The number of machines to be added for each row or rack can beindicated, as well as a position within a rack, thus allowing users toplan the move of machines and follow specific cabling and rackingspecifications. Additionally, identification of failed status can beoverlaid on top of rows, racks, or machines. Information about aparticular element, such as a machine, can include identification andother operationally significant parameters. For example, temperature canbe indicated as a color overlay, from blue to red, indicating hot spotswithin the datacenter. As shown in FIG. 5C, a cabling overlay display550 includes wiring and cabling instructions. The cabling overlaydisplay 550 specifies how, for example, a new server, should beconnected to the two top-of-the-rack switches.

Identification

Several use cases require identification of datacenter elements, orassets. The identification is usually done through a barcode or someother mechanisms such as radio-frequency identification (RFID). Thehandheld device 201 may have different mechanisms to scan theidentifiers. The mechanisms can include, for example, optically scanningby using a camera embedded in the handheld device 201. In thisembodiment, the user can scan one-dimensional or two-dimensional barcodes or other optically based identifiers. Using a reader connectedwirelessly, through, for example, Bluetooth, the user can scancontactless tags like RFID or contact based tags like iButton. Afterreading the identifier, the client software will transmit theidentification to the datacenter management system to retrieve detailsabout a particular asset, or record the asset and its new location. Thismay require the scanning of the asset itself, and the rack (e.g., therack unit) or shelf (e.g., the slot) where the asset has beenpositioned. The identification system, if working with a proximitysensor, can incorporate sufficient spatial resolution to eliminate falsereadings coming from adjacent tags.

Gestures

Gestures are sets of alternative input methods based on movementsdetected by various sensors within the handheld device 201 (see FIG.3A). Aspects of the inventive subject matter described herein can useseveral built in gestures such as to zoom in, zoom out, scroll up ordown, or flip pages. The client application can define new specificgestures. The new specific gestures can include, for example, a swipefrom side-to-side when viewing a rack or a row will switch the view toneighboring racks or rows. Pointing a camera within the handheld device201 up and down a rack can scroll up and down the rack view, allowing aview of various machines from top to bottom (or vice versa). Pointingthe camera within the handheld device 201 up or down a rack can be alsointerpreted as scanning the rack for failed status. The client softwarequeries the datacenter management system for the status of all theelements, components, or machines within the rack.

Datacenter Management System

The datacenter management system can provide the back-end servercomponent for the client software running in the handheld device 201(see FIG. 3A). The client can be connected to the back-end server usinga secure data connection (e.g., HTTPS). In a specific exemplaryembodiment, the datacenter management system can include components suchas, for example, a datacenter model capturing objects within thedatacenter as well as their relationships (e.g., containment, usage, orconnectivity); a protocol interface for the client to communicate withthe server using a service-oriented protocol (e.g., JavaScript ObjectNotation and Representational State Transfer (JSON/REST)); businesslogic implementing the use cases defined, above; a mapping backend toserve maps based on a location of the handheld device 201 (e.g., themapping backend may dynamically generate the maps, or use bitmaps withappropriate coordinates); and communication with the optional radiolocation system 207 (see FIG. 2) and an association with the specificdevice position.

For the racking and wiring task, for example, the datacenter managementsystem provides functions including, for example, management of rackingand wiring requests and their association to the appropriate user;presentation of the request as an overlay on the datacenter map with thenumber of servers to add to each row and can further includecolor-coding to specify different types of machines; presentation ofspecific wiring and racking instructions (e.g., a specific positionwithin the rack, specific connections to the network ports, etc.); andrecording of the actual rack location and wiring (e.g., if a preferredrack location and wiring scheme was not strongly recommended, or if therecommended scheme could not be used).

With reference to FIG. 6, an exemplary relationship model can accomplishvarious tasks, such as those defined, above. The relationship model isshown to include a rack 601, a row 603, and a datacenter 605. Dependingupon a location of the handheld device 201 or a way in which thehandheld device 201 is currently being used (e.g., to optically scan abarcode or electrically scan a proximate RFID tag), a location withinthe rack 601 can display information pertinent to the location. In otherexamples, the handheld device 201 can provide information for an asset609 residing within either a chassis 607 or the rack 601. Thus pertinentrelative dependencies can incorporate and display a relationship used bythe datacenter management system. In the exemplary relationship model,each object has its coordinates specified and can include a graphicalrepresentation that can be used by the client application during mapvisualization.

Radiolocation System

With reference to FIG. 7, an exemplary radio location system 700 is analternative to, or may be used in conjunction with, a GPS-based locationwhen, for example, the building structure is preventing the handhelddevice 201 (not shown explicitly in FIG. 7) from receiving GPS signalsin a portion or all locations within the building. The exemplary radiolocation system 700 is based on a network of several antennas 211A . . .211D. Signal processing boards within a triangulation system 701 detecta location of each handheld device 201 by tuning in to a frequency usedby each handheld device 201. The triangulation system 701 triangulates aposition of each handheld device 201 based on a relative signal strengthreceived by the network of several antennas 211A . . . 211D. Thelocation calculated by the exemplary radio location system 700 is thensent back to the handheld device 201 as a supplement or replacement tothe onboard GPS. Depending upon the exact location of the handhelddevice 201, as well as an operational mode being received from thehandheld device 201, the datacenter management system can providespatially-pertinent information to the handheld device 201.

While various embodiments of the inventive subject matter are describedwith reference to assorted implementations and exploitations, it will beunderstood that these embodiments are illustrative only and that a scopeof the present inventions is not limited merely to those describedembodiments. Moreover, the systems and methods described herein may beimplemented with facilities consistent with any hardware system orhardware systems either defined herein or known independently in the artusing techniques described herein. Many variations, modifications,additions, and improvements are therefore possible.

Modules, Components, and Logic

Additionally, certain embodiments described herein may be implemented aslogic or a number of modules, components, or mechanisms. A module,logic, component, or mechanism (collectively referred to as a “module”)may be a tangible unit capable of performing certain operations and isconfigured or arranged in a certain manner. In certain exemplaryembodiments, one or more computer systems (e.g., a standalone, client,or server computer system) or one or more components of a computersystem (e.g., a processor or a group of processors) may be configured bysoftware (e.g., an application or application portion) or firmware (notethat software and firmware can generally be used interchangeably hereinas is known by a skilled artisan) as a module that operates to performcertain operations described herein.

In various embodiments, a module may be implemented mechanically orelectronically. For example, a module may comprise dedicated circuitryor logic that is permanently configured (e.g., within a special-purposeprocessor) to perform certain operations. A module may also compriseprogrammable logic or circuitry (e.g., as encompassed within ageneral-purpose processor or other programmable processor) that istemporarily configured by software or firmware to perform certainoperations. It will be appreciated that a decision to implement a modulemechanically, in the dedicated and permanently configured circuitry, orin temporarily configured circuitry (e.g., configured by software) maybe driven by cost and time considerations.

Accordingly, the term module should be understood to encompass atangible entity, be that an entity that is physically constructed,permanently configured (e.g., hardwired), or temporarily configured(e.g., programmed) to operate in a certain manner and/or to performcertain operations described herein. Considering embodiments in whichmodules or components are temporarily configured (e.g., programmed),each of the modules or components need not be configured or instantiatedat any one instance in time. For example, where the modules orcomponents comprise a general-purpose processor configured usingsoftware, the general-purpose processor may be configured as respectivedifferent modules at different times. Software may accordingly configurethe processor to constitute a particular module at one instance of timeand to constitute a different module at a different instance of time.

Modules can provide information to, and receive information from, othermodules. Accordingly, the described modules may be regarded as beingcommunicatively coupled. Where multiples of such modules existcontemporaneously, communications may be achieved through signaltransmission (e.g., over appropriate circuits and buses) that connectthe modules. In embodiments in which multiple modules are eitherconfigured or instantiated at different times, communications betweensuch modules may be achieved, for example, through the storage andretrieval of information in memory structures to which the multiplemodules have access. For example, one module may perform an operation,and store the output of that operation in a memory device to which it iscommunicatively coupled. A further module may then, at a later time,access the memory device to retrieve and process the stored output.Modules may also initiate communications with input or output devicesand can operate on a resource (e.g., a collection of information).

Exemplary Machine Architecture and Machine-Readable Medium

With reference to FIG. 8, an exemplary embodiment extends to a machinein the exemplary form of a computer system 800 within whichinstructions, for causing the machine to perform any one or more of themethodologies discussed herein, may be executed. In alternativeexemplary embodiments, the machine operates as a standalone device ormay be connected (e.g., networked) to other machines. In a networkeddeployment, the machine may operate in the capacity of a server or aclient machine in server-client network environment, or as a peermachine in a peer-to-peer (or distributed) network environment. Themachine may be a personal computer (PC), a tablet PC, a set-top box(STB), a Personal Digital Assistant (PDA), a cellular telephone, a webappliance, a network router, a switch or bridge, or any machine capableof executing instructions (sequential or otherwise) that specify actionsto be taken by that machine. Further, while only a single machine isillustrated, the term “machine” shall also be taken to include anycollection of machines that individually or jointly execute a set (ormultiple sets) of instructions to perform any one or more of themethodologies discussed herein.

The exemplary computer system 800 includes a processor 801 (e.g., acentral processing unit (CPU), a graphics processing unit (GPU) orboth), a main memory 803 and a static memory 805, which communicate witheach other via a bus 807. The computer system 800 may further include avideo display unit 809 (e.g., a liquid crystal display (LCD) or acathode ray tube (CRT)). The computer system 800 also includes analpha-numeric input device 811 (e.g., a keyboard), a user interface (UI)navigation device or cursor control device 813 (e.g., a mouse), a diskdrive unit 815, a signal generation device 817 (e.g., a speaker), and anetwork interface device 819.

Machine-Readable Medium

The disk drive unit 815 includes a machine-readable storage medium 821on which is stored one or more sets of instructions and data structures(e.g., software instructions 823) embodying or used by any one or moreof the methodologies or functions described herein. The softwareinstructions 823 may also reside, completely or at least partially,within the main memory 803 or within the processor 801 during executionthereof by the computer system 800; the main memory 803 and theprocessor 801 also constituting machine-readable storage media.

While the machine-readable storage medium 821 is shown in an exemplaryembodiment to be a single medium, the term “machine-readable storagemedium” may include a single medium or multiple media (e.g., acentralized or distributed database, or associated caches and servers)that store the one or more instructions. The term “machine-readablestorage medium” shall also be taken to include any tangible medium thatis capable of storing, encoding, or carrying instructions for executionby the machine and that cause the machine to perform any one or more ofthe methodologies of the present invention, or that is capable ofstoring, encoding, or carrying data structures used by or associatedwith such instructions. The term “machine-readable storage medium” shallaccordingly be taken to include, but not be limited to, solid-statememories, and optical and magnetic media. Specific examples ofmachine-readable storage media include non-volatile memory, including byway of exemplary semiconductor memory devices (e.g., EPROM, EEPROM, andflash memory devices); magnetic disks such as internal hard disks andremovable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.

Transmission Medium

The software instructions 823 may further be transmitted or receivedover a communications network 825 using a transmission medium via thenetwork interface device 819 utilizing any one of a number of well-knowntransfer protocols (e.g., HTTP). Examples of communication networksinclude a local area network (LAN), a wide area network (WAN), theInternet, mobile telephone networks, Plain Old Telephone (POTS)networks, and wireless data networks (e.g., WiFi and WiMax networks).The term “transmission medium” shall be taken to include any intangiblemedium that is capable of storing, encoding, or carrying instructionsfor execution by the machine, and includes digital or analogcommunications signals or other intangible medium to facilitatecommunication of such software.

Although an overview of the inventive subject matter has been describedwith reference to specific exemplary embodiments, various modificationsand changes may be made to these embodiments without departing from thebroader spirit and scope of the present invention. Such embodiments ofthe inventive subject matter may be referred to herein, individually orcollectively, by the term “invention” merely for convenience and withoutintending to voluntarily limit the scope of this application to anysingle invention or inventive concept if more than one is, in fact,disclosed. In general, aspects of the inventive subject matter allow atechnician or other person to locate, update, maintain, replace, orrepair various pieces of electronic equipment of elements with adatacenter. The exemplary embodiments described indicate how atechnician can locate the proper piece of equipment, or location for newor replacement equipment, and follow datacenter protocols and proceduresto properly install or maintain the equipment.

The embodiments illustrated herein are described in sufficient detail toenable those skilled in the art to practice the teachings disclosed.Other embodiments may be used and derived therefrom, such thatstructural and logical substitutions and changes may be made withoutdeparting from the scope of this disclosure. The Detailed Description,therefore, is not to be taken in a limiting sense, and the scope ofvarious embodiments is defined only by the appended claims, along withthe full range of equivalents to which such claims are entitled.

Moreover, plural instances may be provided for resources, operations, orstructures described herein as a single instance. Additionally,boundaries between various resources, operations, modules, engines, anddata stores are somewhat arbitrary, and particular operations areillustrated in a context of specific illustrative configurations. Otherallocations of functionality are envisioned and may fall within a scopeof various embodiments of the present invention. In general, structuresand functionality presented as separate resources in the exemplaryconfigurations may be implemented as a combined structure or resource.Similarly, structures and functionality presented as a single resourcemay be implemented as separate resources.

These and other variations, modifications, additions, and improvementsfall within a scope of the present invention is represented by theappended claims. The specification and drawings are, accordingly, to beregarded in an illustrative rather than a restrictive sense.

What is claimed is:
 1. A system to provide management of a plurality ofelectronic elements in a datacenter, the system comprising: a datacentermanagement system couplable to a wireless network, the datacentermanagement system to receive information regarding a spatial location ofa handheld device within the datacenter, the datacenter managementsystem further to provide information to the handheld device related toeach of the plurality of electronic elements, the datacenter managementsystem including: a management processor having one or more processorsto process information related to each of the plurality of electronicelements; and a database to store information related to each of theplurality of electronic elements.